View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000849 | T99X171.00 SKB Eagle | SW Issue | public | 2020-07-13 17:25 | 2020-09-28 12:05 |
| Reporter | Assigned To | (SW) Kerwin Chen | Due Date | ||
| Priority | urgent | Severity | s2-severe | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Summary | 0000849: [SKB_BTVQ13539]when pairing BA02 RCU, Pairing is failed as code 11 error. | ||||
| Description | hi kerwin we received some report from SKB QA. - F/W ver : 15.520.2-0000 Although they try to pairing with BA02 RCU, It is failed as code 11 error at many times. please check a log and give your test result in your side. Thanks. | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
|
2020-07-13 17:25 developer |
|
|
|
Hi Jason, Please check review results as below: 1. Pairing fail with MD-BRC101 (40:19:20:10:00:07) From the device name, it is not a RCU devices. The pairing device is chosen by TVStorm PairingManager APP. Please check it with TVStorm why APP chooses this device to pair. 2. Pairing fail with 'WHAT_RESET_DISCOVERY_MODE' error There are several cases with 'WHAT_RESET_DISCOVERY_MODE Time Out' in 'BTPairingService' process. From the process ID, we think it is a service in TVStorm Pairing APP. Please help to check with TVStorm when it will print such error during pairing with RCU. BTW, can you reproduce this issue on your side ? We've tried but we don't see this kind of issue here. |
|
|
hi kerwin skb QA try to do factory reset for initialize Box. but still happen error code. Please a log. It can't find MD-BRC101 in a log. 07-14 17:53:07.152 4013 4013 I VAS_BLE_Service: >ACL LINK CONNECTED [null] - checking for supported devices after delay 07-14 17:53:07.152 3893 4305 I bt_stack: [INFO:gatt_api.cc(1109)] GATT_Connectgatt_if=5 40:19:20:10:00:1d 07-14 17:53:07.153 7000 7000 D UEI.SmartControl: --- monitor intent: android.bluetooth.device.action.ACL_CONNECTED 07-14 17:53:36.564 3893 4305 W bt_stack: [WARNING:bta_gattc_act.cc(1040)] bta_gattc_conn_cback: cif=3 connected=0 conn_id=0x0003 reason=0x0022 07-14 17:53:36.564 3893 4305 W bt_stack: [WARNING:bta_gattc_act.cc(1040)] bta_gattc_conn_cback: cif=4 connected=0 conn_id=0x0004 reason=0x0022 |
|
|
Hi Jason, I don't know what happened in these 2 devices. From the log, there are 2 BT devices. STB fail to get the name of both RCUs. And the cod(class of device) of "40:19:20:10:00:1D" is 0x1ff which is not for RCU device. You can check in previous log file(ba02 pairing fail.log), it should be 0x50c. (bt_btif_dm: get_cod remote_cod = 0x0000050c) 07-14 17:53:03.580 4582 4582 D PairingManager: pair() -- START (0) Manager : PAIRING 07-14 17:53:03.580 4582 4582 D PairingManager: checkProcessingState(), manager : PAIRING, Device : PAIRING 07-14 17:53:03.589 4582 4582 I PairingManager: bondDevice(), Bonding success!!! 07-14 17:53:03.593 4582 4582 I PairingManager: pair(), try ( 40:19:20:10:00:1D) name :null Bond state : 11 07-14 17:53:03.593 4582 4582 D PairingManager: pair() -- E N D 07-14 17:53:03.631 4013 4013 I VAS_BLE_Service: BOND STATE CHANGED [null] - was 10, now is 11 ..... 07-14 17:53:50.450 4582 4582 D PairingManager: pair() -- START (0) Manager : PAIRING 07-14 17:53:50.450 4582 4582 D PairingManager: checkProcessingState(), manager : PAIRING, Device : PAIRING 07-14 17:53:50.453 4582 4582 I PairingManager: bondDevice(), Bonding success!!! 07-14 17:53:50.453 4582 4582 I PairingManager: pair(), try ( 40:19:20:10:00:32) name :null Bond state : 10 07-14 17:53:50.454 4582 4582 D PairingManager: pair() -- E N D 07-14 17:53:50.468 4013 4013 I VAS_BLE_Service: BOND STATE CHANGED [null] - was 10, now is 11 |
|
|
Hi kerwin I received some feedback from Movon RCU company. MD-BRC102 is the HCI Module provided as a sample from INTEK Smart3 STB in the replica, and six digits in front of the BT address band are 40:19:20-1XXXX~, which is currently using a similar band to the remote control, probably because of the STB scenario, if STB receives an IR when pairing, it will also attempt to connect to the device that uses the address band 40:19:20~. so it seem be failed . Movon RCU - 40:19:20-2XXXXX HCI mODULE(Bluetooth wifi combo for Intek smart3)- sample : 40:19:20-1XXXXX HCI mODULE(Bluetooth wifi combo for Intek smart3)- prouct later : 40:19:20-6XXXXX it need to clarify mac address. RCU company suggested two method. which method you can support it ? method 1) For devices using the 40:19:20 on the STB side, if the COD is not RCU, is it possible to ignore it and make sure that only RCU can be connected ? method2) If the RCU classification cannot be modified as method 1, STB needs the RCU can be filtered from 40:19:20-200000 to 40:19:20-5FFFFFFF. If you use COD only for devices that receive and connect IR from RCU, regardless of BT address bandwidth, additional COD of remote solution needs to be checked. Case of Movon RCU Because Major Device Class is used as a 'Peripheral(0x500)' device and Minor Device Class as 'Remote Control' (0xC), COD is searched as '0x50C'. (Manufacturer may include 'Keyboard (0x40)' in addition to Remote Control) please give your opinion. and if you modify it and please give a target date. Thanks. |
|
|
hi kerwin also receive a feedback from TVstorm. BA02 RCU seems to have succeeded once in a log. - Fail after timeOut occurs after createBond attempt as below, When the Bluetooth status change as NONE, it will be failed. If normal: after creatingBond -> BluetoothDevice.BOND_BONDING -> BluetoothDevice.BOND_BONDED If failed: Pairing failed after createBond attempt -ond BluetoothDevice.BOND_BONDING -> BluetoothDevice.BOND_NONE it need to check by STB. |
|
|
Hi Jason, For MAC address issue, I think it should be handled in Pairing APP, not in BT stack. BT stack should pass all discovered BT devices to APP, then APP choose which device to be paired. For example, there is a 'Remotes& Accessories' page in Android Setting. It receives all discovered BT devices from BT stack, but only looks for 'Remotes' and other supported devices. |
|
|
Hi Jason, For TVStorm, I am asking when it will show 'WHAT_RESET_DISCOVERY_MODE' timeout error. Does 'WHAT_RESET_DISCOVERY_MODE' equal to BOND_NONE ? |
|
|
hi kerwin see a feedback from TVstorm WHAT_RESET_DISCOVERY_MODE Time out is not the same as BOND_NONE. Previously, the HID connection with RCU company was defined as 25 seconds / A2dp connection as 35 seconds. The RCU's HID is valid for 25 seconds until discover -> pair -> connect and after only wait for 25 seconds, a paring app is terminated. In some cases, and it can also occur during pair attempts and scan can't be done during discover. Thanks |
|
|
Hi Jason, I don't understand about TVStorm's comments. Please check log in "ba02 pairing fail.log" as below Pairing APP already finish discover for RCU device and start to bond with target RCU Why 'WHAT_RESET_DISCOVERY_MODE' error occurs ? =========== partial log in ba02 pairing fail.log ================== 07-10 17:18:06.821 4176 4176 D MainActivity: Pairing - Start 07-10 17:18:06.824 4092 4092 I PairingManager: =====CHECK DEVICE===== :14:4E:34:F0:12:5A BRM_BA02_25A 07-10 17:18:06.824 4092 4092 I PairingManager: =====CHECK DEVICE===== :F4:7D:EF:F7:0E:ED Galaxy Buds (0EED) 07-10 17:18:06.825 4092 4092 D PairingManager: startDiscovery() -- START 07-10 17:18:06.826 4092 4092 I PairingManager: startDiscovery(), SCANNING_DEVICE 07-10 17:18:06.830 4092 4092 D PairingManager: startDiscovery() -- E N D 07-10 17:18:06.831 4092 4092 D BTPairingService: showToastMessage(), toast message : 리모컨 연결을 시도 중입니다. 07-10 17:18:06.835 4092 4092 I BTPairingService: setDiscoveryEnable(), isEnable : false 07-10 17:18:08.942 4092 4092 D PairingManager: foundDevice() -- START 07-10 17:18:08.942 4092 4092 I PairingManager: foundDevice(), Found device!!!, SCANNING_DEVICE 07-10 17:18:08.942 4092 4092 D PairingManager: changeState() -- START(UNKNOW) 07-10 17:18:08.947 4092 4092 D PairingManager: cancelDiscovery() -- START 07-10 17:18:08.947 4092 4092 D PairingManager: cancelDiscovery - Processing status : PAIRING 07-10 17:18:08.950 4092 4092 D PairingManager: cancelDiscovery() -- E N D 07-10 17:18:08.950 4092 4092 D PairingManager: changeState(), Manager : PAIRING, Device : PAIRING_PREPARE 07-10 17:18:08.950 4092 4092 D PairingManager: changeState() -- E N D 07-10 17:18:08.954 4092 4092 D PairingManager: createBond() -- START 07-10 17:18:08.954 4092 4092 I PairingManager: createBond(), Start pairing!!, PAIRING 07-10 17:18:08.954 4092 4092 D PairingManager: changeState() -- START(PAIRING_PREPARE) 07-10 17:18:08.968 4092 4092 D BTPairingService: showToastMessage(), toast message : 리모컨을 연결 중입니다. [BMM_BA02_0E5] 07-10 17:18:08.995 4092 4092 D PairingManager: changeState(), Manager : PAIRING, Device : PAIRING 07-10 17:18:08.995 4092 4092 D PairingManager: changeState() -- E N D 07-10 17:18:08.995 4092 4092 D PairingManager: createBond() -- E N D 07-10 17:18:08.995 4092 4092 D PairingManager: foundDevice() -- E N D 07-10 17:18:09.050 4092 4092 D PairingManager: pair() -- START (0) Manager : PAIRING 07-10 17:18:09.050 4092 4092 D PairingManager: checkProcessingState(), manager : PAIRING, Device : PAIRING 07-10 17:18:09.053 4092 4092 I PairingManager: bondDevice(), Bonding success!!! 07-10 17:18:09.056 4092 4092 I PairingManager: pair(), try ( 40:19:20:10:00:E5) name :BMM_BA02_0E5 Bond state : 10 07-10 17:18:09.056 4092 4092 D PairingManager: pair() -- E N D 07-10 17:18:11.627 4723 4777 D AGENT : ###remoconisPairing : false 07-10 17:18:31.865 4092 4092 I BTPairingService: WHAT_RESET_DISCOVERY_MODE Time Out 07-10 17:18:31.865 4092 4092 I PairingManager: timeOutPairing() 07-10 17:18:31.865 4092 4092 D BTPairingService: onNotifyFailed(), Manager : PAIRING, Device : PAIRING_FAIL 07-10 17:18:31.881 4092 4092 D BTPairingService: showToastMessage(), toast message : [BMM_BA02_0E5] 리모컨 연결에 실패하였습니다. 07-10 17:18:31.881 4092 4092 D BTPairingService: (Bonding 실패) - Code 11 |
|
|
hi kerwin according to modify it by TvStorm, this issue is resolved from v15.520.5 fw. Thanks. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-07-13 17:25 |
|
New Issue | |
| 2020-07-13 17:25 |
|
Status | new => assigned |
| 2020-07-13 17:25 |
|
Assigned To | => (SW) Kerwin Chen |
| 2020-07-13 17:25 |
|
File Added: ba02 pairing fail.log | |
| 2020-07-13 17:25 |
|
File Added: CODE11.jpg | |
| 2020-07-14 10:37 | (SW) Kerwin Chen | Note Added: 0003755 | |
| 2020-07-14 17:15 |
|
File Added: 20200714_175257.log | |
| 2020-07-14 17:15 |
|
Note Added: 0003759 | |
| 2020-07-14 19:26 | (SW) Kerwin Chen | Note Added: 0003760 | |
| 2020-07-14 19:28 | (SW) Kerwin Chen | Note Edited: 0003760 | |
| 2020-07-16 16:39 |
|
Note Added: 0003776 | |
| 2020-07-16 16:44 |
|
Note Added: 0003777 | |
| 2020-07-16 17:07 | (SW) Kerwin Chen | Note Added: 0003778 | |
| 2020-07-16 17:12 | (SW) Kerwin Chen | Note Added: 0003780 | |
| 2020-07-17 10:24 |
|
Note Added: 0003787 | |
| 2020-07-17 12:49 | (SW) Kerwin Chen | Note Added: 0003789 | |
| 2020-08-03 09:21 |
|
Note Added: 0003913 | |
| 2020-08-03 09:21 |
|
Status | assigned => resolved |
| 2020-08-03 09:21 |
|
Resolution | open => fixed |
| 2020-09-28 12:05 |
|
Status | resolved => closed |
